test: remove otel skip statement #10145

rogercoll · 2025-09-25T09:04:13Z

What does this PR do?

Fixes #10020

Upstream fix of Helm Chart uninstallation open-telemetry/opentelemetry-helm-charts#1877

Why is it important?

Any deployment of the kube-stack Helm Chart prior to v0.10.5 version cannot be uninstalled.

Checklist

I have read and understood the pull request guidelines of this project.
My code follows the style guidelines of this project
I have commented my code, particularly in hard-to-understand areas
I have made corresponding changes to the documentation
I have made corresponding change to the default configuration files
I have added tests that prove my fix is effective or that my feature works
I have added an entry in ./changelog/fragments using the changelog tool
I have added an integration test or an E2E test

Disruptive User Impact

How to test this PR locally

Related issues

Questions to ask yourself

How are we going to support this in production?
How are we going to measure its adoption?
How are we going to debug this?
What are the metrics I should take care of?
...

mergify · 2025-09-25T09:04:50Z

This pull request does not have a backport label. Could you fix it @rogercoll? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

backport-./d./d is the label that automatically backports to the 8./d branch. /d is the digit
backport-active-all is the label that automatically backports to all active branches.
backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

rogercoll · 2025-09-26T09:07:53Z

buildkite test this

elastic-sonarqube · 2025-09-30T09:34:02Z

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube

elasticmachine · 2025-09-30T17:48:52Z

💚 Build Succeeded

Buildkite Build
Commit: f8f64be

History

💔 Build #27785 failed e8acf8d
💔 Build #27780 failed 970e392
💔 Build #27730 failed 94fcb6f
💔 Build #27586 failed 164d3b0
💔 Build #27532 failed b1bea40

cc @rogercoll

rubenruizdegauna

LGTM

elasticmachine · 2025-10-01T09:34:12Z

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

rogercoll · 2025-10-01T12:51:02Z

buildkite test this

github-actions · 2025-10-06T14:43:57Z

@Mergifyio backport 8.18 8.19 9.0 9.1 9.2

mergify · 2025-10-06T14:44:12Z

backport 8.18 8.19 9.0 9.1 9.2

✅ Backports have been created

#10348 [8.18] (backport #10145) test: remove otel skip statement has been created for branch 8.18
#10349 [8.19] (backport #10145) test: remove otel skip statement has been created for branch 8.19
#10350 [9.0] (backport #10145) test: remove otel skip statement has been created for branch 9.0
#10351 [9.1] (backport #10145) test: remove otel skip statement has been created for branch 9.1
#10352 [9.2] (backport #10145) test: remove otel skip statement has been created for branch 9.2

* test: remove otel skip statement * chore: bump kube-stack Helm Chart to 0.9.4 * chore: bump kube-stack to 0.10.4 * chore: bump kube-stack to 0.10.5 --------- Co-authored-by: Ruben Ruiz de Gauna <[email protected]> (cherry picked from commit b74a86b)

* test: remove otel skip statement * chore: bump kube-stack Helm Chart to 0.9.4 * chore: bump kube-stack to 0.10.4 * chore: bump kube-stack to 0.10.5 --------- (cherry picked from commit b74a86b) Co-authored-by: Roger Coll <[email protected]> Co-authored-by: Ruben Ruiz de Gauna <[email protected]>

## Summary New kube-stack version that fixes Chart uninstallation for any version prior 0.10.5: open-telemetry/opentelemetry-helm-charts#1876 elastic-agent PR: elastic/elastic-agent#10145 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... --------- Co-authored-by: Joe Reuter <[email protected]> Co-authored-by: kibanamachine <[email protected]>

## Summary New kube-stack version that fixes Chart uninstallation for any version prior 0.10.5: open-telemetry/opentelemetry-helm-charts#1876 elastic-agent PR: elastic/elastic-agent#10145 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... --------- Co-authored-by: Joe Reuter <[email protected]> Co-authored-by: kibanamachine <[email protected]> (cherry picked from commit e63084b)

## Summary New kube-stack version that fixes Chart uninstallation for any version prior 0.10.5: open-telemetry/opentelemetry-helm-charts#1876 elastic-agent PR: elastic/elastic-agent#10145 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... --------- Co-authored-by: Joe Reuter <[email protected]> Co-authored-by: kibanamachine <[email protected]>

* test: remove otel skip statement * chore: bump kube-stack Helm Chart to 0.9.4 * chore: bump kube-stack to 0.10.4 * chore: bump kube-stack to 0.10.5 --------- (cherry picked from commit b74a86b) Co-authored-by: Roger Coll <[email protected]> Co-authored-by: Ruben Ruiz de Gauna <[email protected]>

* test: remove otel skip statement (#10145) * test: remove otel skip statement * chore: bump kube-stack Helm Chart to 0.9.4 * chore: bump kube-stack to 0.10.4 * chore: bump kube-stack to 0.10.5 --------- Co-authored-by: Ruben Ruiz de Gauna <[email protected]> (cherry picked from commit b74a86b) * override upstream k8sattributes configuration * override logs-only configuration --------- Co-authored-by: Roger Coll <[email protected]> Co-authored-by: Ruben Ruiz de Gauna <[email protected]>

New kube-stack version that fixes Chart uninstallation for any version prior 0.10.5: open-telemetry/opentelemetry-helm-charts#1876 elastic-agent PR: elastic/elastic-agent#10145 Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... --------- Co-authored-by: Joe Reuter <[email protected]> Co-authored-by: kibanamachine <[email protected]> (cherry picked from commit e63084b)

## Summary New kube-stack version that fixes Chart uninstallation for any version prior 0.10.5: open-telemetry/opentelemetry-helm-charts#1876 elastic-agent PR: elastic/elastic-agent#10145 ### Checklist Check the PR satisfies following conditions. Reviewers should verify this PR satisfies this list as well. - [ ] Any text added follows [EUI's writing guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses sentence case text and includes [i18n support](https://github.com/elastic/kibana/blob/main/src/platform/packages/shared/kbn-i18n/README.md) - [ ] [Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html) was added for features that require explanation or tutorials - [ ] [Unit or functional tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html) were updated or added to match the most common scenarios - [ ] If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the [docker list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker) - [ ] This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The `release_note:breaking` label should be applied in these situations. - [ ] [Flaky Test Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was used on any tests changed - [ ] The PR description includes the appropriate Release Notes section, and the correct `release_note:*` label is applied per the [guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process) - [ ] Review the [backport guidelines](https://docs.google.com/document/d/1VyN5k91e5OVumlc0Gb9RPa3h1ewuPE705nRtioPiTvY/edit?usp=sharing) and apply applicable `backport:*` labels. ### Identify risks Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss. Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging. - [ ] [See some risk examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx) - [ ] ... --------- Co-authored-by: Joe Reuter <[email protected]> Co-authored-by: kibanamachine <[email protected]>

test: remove otel skip statement

97fff4d

mergify bot assigned rogercoll Sep 25, 2025

rogercoll added the skip-changelog label Sep 25, 2025

Merge branch 'main' into fix_otel_k8s_flaky

b1bea40

Merge branch 'main' into fix_otel_k8s_flaky

164d3b0

rogercoll mentioned this pull request Sep 26, 2025

[Flaky Test]: TestOtelKubeStackHelm – test timed out after 2h0m0s #10020

Closed

rogercoll added 5 commits September 29, 2025 16:06

Merge branch 'main' into fix_otel_k8s_flaky

429b354

chore: bump kube-stack Helm Chart to 0.9.4

94fcb6f

Merge branch 'main' into fix_otel_k8s_flaky

970e392

Merge branch 'main' into fix_otel_k8s_flaky

36c7b6f

chore: bump kube-stack to 0.10.4

e8acf8d

chore: bump kube-stack to 0.10.5

f8f64be

Merge branch 'main' into fix_otel_k8s_flaky

6794632

rogercoll marked this pull request as ready for review October 1, 2025 07:53

rogercoll requested a review from a team as a code owner October 1, 2025 07:53

rogercoll requested review from rubenruizdegauna and straistaru October 1, 2025 07:53

Merge branch 'main' into fix_otel_k8s_flaky

07e0feb

rubenruizdegauna approved these changes Oct 1, 2025

View reviewed changes

rubenruizdegauna enabled auto-merge (squash) October 1, 2025 08:52

rubenruizdegauna disabled auto-merge October 1, 2025 08:58

rubenruizdegauna self-requested a review October 1, 2025 09:33

pierrehilbert added the Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team label Oct 1, 2025

Merge branch 'main' into fix_otel_k8s_flaky

6f896e7

rogercoll enabled auto-merge (squash) October 1, 2025 12:50

rogercoll merged commit b74a86b into elastic:main Oct 1, 2025
20 of 21 checks passed

rogercoll mentioned this pull request Oct 2, 2025

chore: bump kube-stack Helm chart onboarding to 0.10.5 elastic/kibana#237227

Merged

10 tasks

rogercoll added the backport-active-all Automated backport with mergify to all the active branches label Oct 6, 2025

mergify bot mentioned this pull request Oct 6, 2025

[8.18] (backport #10145) test: remove otel skip statement #10348

Merged

8 tasks

This was referenced Oct 6, 2025

[8.19] (backport #10145) test: remove otel skip statement #10349

Merged

[9.0] (backport #10145) test: remove otel skip statement #10350

Merged

mergify bot mentioned this pull request Oct 6, 2025

[9.1] (backport #10145) test: remove otel skip statement #10351

Merged

8 tasks

mergify bot mentioned this pull request Oct 6, 2025

[9.2] (backport #10145) test: remove otel skip statement #10352

Merged

8 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

test: remove otel skip statement #10145

test: remove otel skip statement #10145

Uh oh!

rogercoll commented Sep 25, 2025 •

edited

Loading

Uh oh!

mergify bot commented Sep 25, 2025

Uh oh!

rogercoll commented Sep 26, 2025

Uh oh!

elastic-sonarqube bot commented Sep 30, 2025

Uh oh!

elasticmachine commented Sep 30, 2025

Uh oh!

rubenruizdegauna left a comment

Uh oh!

elasticmachine commented Oct 1, 2025

Uh oh!

rogercoll commented Oct 1, 2025

Uh oh!

Uh oh!

github-actions bot commented Oct 6, 2025

Uh oh!

mergify bot commented Oct 6, 2025 •

edited

Loading

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

test: remove otel skip statement #10145

test: remove otel skip statement #10145

Uh oh!

Conversation

rogercoll commented Sep 25, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

What does this PR do?

Why is it important?

Checklist

Disruptive User Impact

How to test this PR locally

Related issues

Questions to ask yourself

Uh oh!

mergify bot commented Sep 25, 2025

Uh oh!

rogercoll commented Sep 26, 2025

Uh oh!

elastic-sonarqube bot commented Sep 30, 2025

Quality Gate passed

Uh oh!

elasticmachine commented Sep 30, 2025

💚 Build Succeeded

History

Uh oh!

rubenruizdegauna left a comment

Choose a reason for hiding this comment

Uh oh!

elasticmachine commented Oct 1, 2025

Uh oh!

rogercoll commented Oct 1, 2025

Uh oh!

Uh oh!

github-actions bot commented Oct 6, 2025

Uh oh!

mergify bot commented Oct 6, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

✅ Backports have been created

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

rogercoll commented Sep 25, 2025 •

edited

Loading

mergify bot commented Oct 6, 2025 •

edited

Loading